Techniques for managing mobility management signaling in a wireless network

ABSTRACT

Techniques are described that can be used for efficient mobility management signaling. In some cases, a network can specify an extended timer used for a machine to machine (M2M) type device to communicate with a network. The extended timer can be transmitted in connection with an attachment acceptance message, Location Updating Accept message, Tracking Area Update Accept, or Routing Area Update Accept message. In some cases, a timer can be adjusted using a multiplier in order to increase a period at which communications with the network occur. The network can transmit an indication to change a timer by multiplying the timer with the multiplier.

RELATED ART

This application is related to U.S. Patent Application No. 61/373,788,filed Aug. 13, 2010 (attorney docket no. P35732Z) and claims prioritytherefrom.

FIELD

The subject matter disclosed herein relates generally to techniques forestablishing timers for network communication.

Related Art

Devices such as refrigerators, televisions, and coffee makers usenetworks to communicate with other devices. Machine to Machine (M2M)communication refers to the exchange of data between devices. M2Mcommunication can be used for areas such as security (e.g., surveillancesystems), asset tracking (e.g., fleet management, asset tracking, pay asyou go, navigation), payment (e.g., point of sales and vendingmachines), metering (e.g., power, gas, water, and smart grid control),health care (e.g., remote diagnostics), and other consumer devices(e.g., digital photo frame, digital camera, net books, tablets, bookreaders, set top boxes, and gaming consoles).

If many of these M2M devices, including embedded/connected consumerdevices, attach or roam in existing wide area wireless networks (e.g.,3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) orIEEE 802.16) then the existing wireless networks may become burdenedwith congestion. It is therefore desirable to provide a solution forsignaling congestion and overload control due to devices that performM2M communications attaching and communicating with the network.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention are illustrated by way of example,and not by way of limitation, in the drawings and in which likereference numerals refer to similar elements.

FIG. 1 depicts an example of devices connected using a wireless network.

FIG. 2 depicts an example of a communication from a network to a mobiledevice to set a timing of Periodic Location Area Update procedures.

FIG. 3 depicts an example format of a communication transmitted from anetwork to a device that indicates whether the device is to adjust aPeriodic Location Area Update timer using a multiplier.

FIG. 4 depicts an example manner that a mobile station can receive aLocation Area Update timer multiplier from a network.

FIG. 5 depicts a procedure for setting a Periodic Routing Area UpdateTimer as part of routing area updates.

FIG. 6 depicts a procedure for setting a Periodic Tracking Area Updatetimer as part of tracking area updates.

FIG. 7 depicts a procedure that can be used to transmit a PeriodicRouting Area Update Timer or Periodic Tracking Area Update Timer as partof an attach procedure.

FIG. 8 provides an example of a system in accordance with an embodiment.

DETAILED DESCRIPTION

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present invention. Thus, theappearances of the phrase “in one embodiment” or “an embodiment” invarious places throughout this specification are not necessarily allreferring to the same embodiment. Furthermore, the particular features,structures, or characteristics may be combined in one or moreembodiments.

Embodiments of the invention may be used in a variety of applications.Some embodiments of the invention may be used in conjunction withvarious devices and systems, for example, a transmitter, a receiver, atransceiver, a transmitter-receiver, a wireless communication station, awireless communication device, a wireless Access Point (AP), a modem, awireless modem, a Personal Computer (PC), a desktop computer, a mobilecomputer, a laptop computer, a notebook computer, a tablet computer, aserver computer, a handheld computer, a handheld device, a PersonalDigital Assistant (PDA) device, a handheld PDA device, a network, awireless network, a Local Area Network (LAN), a Wireless LAN (WLAN), aMetropolitan Area Network (MAN), a Wireless MAN (WMAN), a Wide AreaNetwork (WAN), a Wireless WAN (WWAN), devices and/or networks operatingin accordance with existing IEEE 802.11, 802.11a, 802.11b, 802.11e,802.11g, 802.11 h, 802.11i, 802.11n, 802.16, 802.16d, 802.16e, 802.16m,3GPP standards, physical layer description of 3GPP LTE advanced 36211release 10, and/or future versions and/or derivatives and/or Long TermEvolution (LTE) of the above standards, a Personal Area Network (PAN), aWireless PAN (WPAN), units and/or devices which are part of the aboveWLAN and/or PAN and/or WPAN networks, one way and/or two-way radiocommunication systems, cellular radio-telephone communication systems, acellular telephone, a wireless telephone, a Personal CommunicationSystems (PCS) device, a PDA device which incorporates a wirelesscommunication device, a Multiple Input Multiple Output (MIMO)transceiver or device, a Single Input Multiple Output (SIMO) transceiveror device, a Multiple Input Single Output (MISO) transceiver or device,a Multi Receiver Chain (MRC) transceiver or device, a transceiver ordevice having “smart antenna” technology or multiple antenna technology,or the like. In addition, embodiments can be used for M2M devices andapplications.

Some embodiments of the invention may be used in conjunction with one ormore types of wireless communication signals and/or systems, forexample, Radio Frequency (RF), Infra Red (IR), Frequency-DivisionMultiplexing (FDM), Orthogonal FDM (OFDM), Orthogonal Frequency DivisionMultiple Access (OFDMA), Time-Division Multiplexing (TDM), Time-DivisionMultiple Access (TDMA), Extended TDMA (E-TDMA), General Packet RadioService (GPRS), Extended GPRS, Code-Division Multiple Access (CDMA),Wideband CDMA (WCDMA), CDMA 2000, Multi-Carrier Modulation (MDM),Discrete Multi-Tone (DMT), Bluetooth(®), ZigBee(™), or the like.Embodiments of the invention may be used in various other apparatuses,devices, systems and/or networks.

Many devices involved in M2M communications can use a network in limitedways. For example, M2M devices can be low mobility, involve timecontrolled network-use, are time tolerant, are packet switched (PS)only, utilize small data transmissions, use mobile originatedcommunications only, and communicate based on a location-specifictrigger. For example, devices that use M2M for smart metering havecharacteristics of being low-mobility, low-power use, low datatransmission use, and time tolerance. Various embodiments potentiallyprovide a solution for efficient of Mobility Management (MM) proceduresfor M2M devices. Various embodiments potentially provide signalingcongestion and overload control mechanisms for M2M and/or human to human(H2H) devices. H2H devices can include, but are not limited to, mobilephones, smart phones, and radios that allow communication among people.Various embodiments potentially provide a manner for low-mobility andlow-power consuming M2M devices to connect with a network while reducingload to the network.

Various embodiments provide methods to optimize MM procedures (e.g.,periodic location/routing/tracking area update procedures) at least forlow-mobility and/or low-power consuming M2M devices using at least 3GPPcompliant networks (e.g., GSM, GPRS, EDGE, UMTS, HSUPA, HSDPA, HSPA, andLTE) and/or other wireless networks. 3GPP LTE is described in 3GPP LTERel-8 (2008) specifications as well as variations thereof. Variousembodiments can provide a signaling congestion and overload controlmechanism for a network due to attachment of roaming/non-roaming M2Mdevices. In some cases, various embodiments can also apply to some H2Hdevices (e.g., in circuit switched domain) to potentially optimize MM,signaling congestion, and overload control procedures.

Periodic updating may be used to periodically notify the availability ofthe mobile station to the network. 3GPP TS 24.008 and 3GPP TS 24.301V10.0.0 (2010) specify mobility management procedures for devices thatinvolve periodic Location Area Update (LAU), periodic Routing AreaUpdate (RAU), and periodic tracking area update (TAU) procedures. 3GPPTS 24.008 and 3GPP TS 24.301 V10.0.0 (2010) also describe communicationsof International Mobile Subscriber Identity (IMSI) attach procedures.IMSI attach procedures can be used when a device is powered-on so thatthe device can register with a network. Those procedures can be used toperiodically notify the availability of user elements (UE) to thenetwork. In general, TS 24.008 provides L3/NAS specification for pre-LTE3GPP systems (e.g., GSM, GPRS, EDGE, UMTS, and HSPA) whereas TS 24.301provides L3/NAS procedures for LTE.

For example, in the UE, timing of periodic LAU procedures can becontrolled by the timer T3212. T3212 is broadcast in the L3-RR SYSTEMINFORMATION TYPE 3 message on the BCCH, in the CONTROL CHANNELDESCRIPTION Information Element (IE) (specified in 3GPP TS 44.018subclause 10.5.2.11). In general, TS 44.018 provides RRC specificationfor pre-LTE 3GPP systems (i.e., GSM, GPRS, EDGE, UMTS, and HSPA) and canbe used as a reference for L3 system broadcast messages. Variousembodiments provide an efficient method for periodic LAU forlow-mobility devices to optimize MM signaling or to reduce networkcongestion. In some embodiments, for periodic LAU procedures, a UE canbe programmed or configured with a T3212_Multiplier. Alternatively, insome embodiments, T3212_Multiplier or T3212_Multiplier_Indication can besent by the network inside CONTROL_CHANNEL DESCRIPTION IE of an L3-RRSYSTEM INFORMATION TYPE 3 message.

In various embodiments, the T3212_Multiplier can be used to increase aperiod at which periodic LAU occurs by calculating the new extendedT3212 timer value by multiplying the T3212_Multiplier with the T3212timer received in L3-RR SYSTEM INFORMATION TYPE 3 message. In someembodiments, a T3212_Multiplier or a new extended T3212 timer can beconfigured at an HSS/HLR and downloaded to network (e.g., MSC/SGSN) aspart of an Insert Subscriber Data procedure and then transmitted by thenetwork to a UE in a LOCATION AREA UPDATE ACCEPT message. In someembodiments, a T3212_Multiplier or a new extended T3212 timer can bedirectly configured at network (MSC/SGSN) and transmitted to a UE in aLOCATION AREA UPDATE ACCEPT message. In some embodiments, a maximumvalue of the new extended timer T3212 can be 310 hours, although othermaximum values can be defined.

The frequency of a periodic RAU procedure is controlled in the UE by theperiodic Routing Area (RA) update timer, T3312. The value of timer T3312is transmitted to the UE in one or more of the messages ROUTING AREAUPDATE ACCEPT and/or ATTACH ACCEPT. T3312 is currently defined as typeGPRS timer. Per current encoding (defined in TS 24.008), GPRS timer canhave maximum value of 31 decihours. However, the maximum value limit isnot efficient for low-mobility M2M devices. Various mechanisms forextending the T3312 timer are described herein. In some embodiments, thenew extended T3312 timer can be stored in HLR/HSS as part of UEsubscription data and downloaded to network (SGSN) as part of an InsertSubscriber Data procedure and then transmitted by the network (SGSN) toa UE in a ROUTING AREA UPDATE ACCEPT and/or ATTACH ACCEPT message. Insome embodiments, the new extended T3312 timer can be directlyconfigured at the network (e.g., SGSN) and then transmitted to a UE in aROUTING AREA UPDATE ACCEPT and/or ATTACH ACCEPT message.

In some embodiments, new encoding values of T3312 timer can defined inorder to extend the timer value beyond 31 decihours. The extension canbe identified as T3312ext value. In some cases, T3312ext value can be 3octets or 24 bits. For example, T3312ext value can be defined in asimilar manner to that of GPRS Timer 3 of TS 24.008. Octet 3 of T3312extvalue can be defined as follows: (a) bits 5 to 1 represent the binarycoded timer value and (b) bits 8 to 6 define the timer value unit forthe GPRS timer. For example, bits 8 to 6 can be defined as follows:

0 0 0 value is incremented in multiples of 10 minutes 0 0 1 value isincremented in multiples of 1 hour 0 1 0 value is incremented inmultiples of 10 hours 1 1 1 value indicates that the timer isdeactivated.Accordingly, a maximum value of T3312ext value can be 310 hours.However, the bits 8 to 6 can be redefined to include larger or smallerincrements to enlarge or reduce the maximum value of T3312ext value. Forexample, values 011 and 100 can be defined for an increment larger than10 hour increments.

The value of the timer can be unique within an RA. The timer T3312 canbe deactivated so that UE performs no periodic RA by specifying aninfinite value for the timer. If the timer T3312ext value can beprovided by the network, then the MS shall use the timer T3312ext valueas a periodic RAU timer. If the timer T3312ext value is not provided bythe network, then the MS shall use the timer T3312 value as a periodicRAU timer (T3312).

The frequency of a periodic TAU procedure is controlled in the UE by thetimer T3412. In various embodiments, the value of timer T3412 istransmitted to the UE in one or more of the TRACKING AREA UPDATE ACCEPTmessages and/or ATTACH ACCEPT. T3412 is currently defined as of typeGPRS timer. Per current encoding (defined in TS 24.301), GPRS timer canhave maximum value of 31 decihours. The maximum value may not beefficient for low-mobility M2M devices. Various embodiments providemanners for extending the T3412 timer. In some embodiments, the newextended T3412 timer can be stored in HLR/HSS as part of UE subscriptiondata and downloaded to network (e.g., SGSN/MME) as part of an InsertSubscriber Data procedure and then transmitted by the network (SGSN/MME)to a UE in a TRACKING AREA UPDATE ACCEPT and/or ATTACH ACCEPT message.In some embodiments, the new extended T3412 timer can directlyconfigured at the network (e.g., SGSN/MME) and then transmitted to a UEin a TRACKING AREA UPDATE ACCEPT and/or ATTACH ACCEPT message.

In some embodiments, new encoding values of T3412 timer can be definedin order to extend the timer value beyond 31 decihours. The extensioncan be identified as T3412ext value. In some cases, T3412ext value canbe 3 octets or 24 bits. The T3412ext value can be defined in a similarmanner as that of T3312ext value. The UE can apply this timer in thelist of tracking areas assigned to the UE. If the timer T3412ext valueis provided by the network, then UE shall use the value in timerT3412ext value IE as a periodic TAU timer (T3412). If the timer T3412extvalue IE is not provided by the network, then the UE shall use the valuein timer T3412 value IE as a periodic TAU timer.

If the received timer contains an indication that the timer isdeactivated or the timer value is zero, then the UE shall not perform aperiodic updating procedure.

FIG. 1 depicts an example of devices connected using a wireless network.The network can be compliant with any variety of IEEE 802.16 or 3GPP LTEas well as variations and revisions thereof. In the downstream ordownlink case, the generically-named transmitters 102 and/or 202 abovemay be interchangeably referred to as a base station (BS), Node B (NB),enhanced Node B (eNB), or access point (AP). In various embodiments, forthe downlink, the transmitter can also be interchangeably referred to asnetwork entities such as a Mobile Switching Center (MSC), Serving GPRSSupport Node (SGSN), or Mobility Management Entity (MME). In thisdownlink case, the receivers 104 and/or 204 above may be interchangeablyreferred to as a mobile station (MS), subscriber station (SS), userequipment (UE), station (STA), machine-type communication (MTC) device,or machine-to-machine (M2M) device at the system level herein. Further,the terms BS, NB, eNB, AP, MSC, SGSN, and MME may be conceptuallyinterchanged, depending on which wireless protocol is being used, so areference to BS herein may also be seen as a reference to any of NB,eNB, AP, MSC, SGSN, and MME. Similarly, a reference to MS or SS hereinmay also be seen as a reference to any of UE, STA, an MTC device, or M2Mdevice.

In various embodiments, each transmitter and receiver includes anon-access stratum (NAS) that can be used to transmit and interpretmessages used to control timing of location area updates, routing areaupdates, and/or tracking area update.

FIG. 2 depicts an example of a communication from a network to a mobiledevice to set a timing of Location Area Update procedures. Thecommunication from network 202 can be transmitted using a base stationcontroller (BSC), radio network controller (RNC), or another device.

MS 204 can be incorporated into a UE, an MTC device, an M2M device, orother types of devices. MS 204 uses a T3212_Timer, T3212_Timer, todetermine when to perform LAU procedures. T3212_Timer can be a periodicLAU timer with specific encoding applying to M2M devices. T3212_Timercan be provisioned in MS 204 and network 202. 3GPP TS 44.018 version10.0.0 (2010) subclause 10.5.2.11 specifies that a value for T3212_Timeris broadcast in the L3-RR SYSTEM INFORMATION TYPE 3 message on theBroadcast Control Channel (BCCH) in the control channel descriptioninformation element (IE). For circuit switched (CS) domain specificsystems, a period of LAU procedures is the same for all the devices in aspecific area because T3212 is broadcast in the L3-RR SYSTEM INFORMATIONTYPE 3 message on the BCCH.

T3212 timeout value field can have a range between 0 to 255. The timervalue 0 is used for infinite timeout value, i.e. periodic updating shallnot be used within the cell.

In various embodiments, MS 204 can be programmed or configured withmultiplier T3212_Multiplier. In some embodiments, MS 204 may obtainT3212_Multiplier by randomly selecting a value from a configured range.In some embodiments, network 202 transmits T3212_Multiplier in an octet5 that can be added to a Control Channel Descriptor IE of L3-RR SYSTEMINFORMATION TYPE 3 message shown in FIG. 3. In some embodiments, T3212_Multiplier can be transmitted to MS 204 as part of LOCATION AREA UPDATEACCEPT message. LOCATION AREA UPDATE ACCEPT message is described forexample in TS 24.008 version 10.0.0 (2010), although other formats canbe used. In some embodiments, the spare bits of octet 3 of ControlChannel Descriptor IE of L3-RR SYSTEM INFORMATION TYPE 3 message can beused to transmit a T3212_Multiplier.

In some embodiments, it is desirable to have a longer/extended T3212timeout period to reduce the frequency of periodic LAU. Network 202 cantransmit to MS 204 an indication of whether to use T3212_Multiplier toincrease an interval between periodic LAU. An indicator can betransmitted in spare bytes of Octet 3 of the communication of FIG. 3.The indicator can be 1 bit. The indicator can be positioned in bit 8 ofoctet 3, although other locations can be used. In cases where thetimeout period is to be increased, MS 204 can multiply theT3212_Multiplier by timer T3212 to increase an interval between periodicLAU. In other words, MS 204 can use the longer/extended periodic LAUtimer that is the product of timer T3212 with T3212_Multiplier. Forexample, after a device configured with multiplier of 2 receives anindication to use the multiplier, the device can change LAU from 10updates per minute to 5 updates per minute. MS 204 can thereafter usethe product of the T3212_Multiplier and the T3212 timer for the periodicLAU without further instruction from network 202.

FIG. 3 depicts an example format of a communication transmitted from anetwork to a device that indicates whether the device is to adjust aperiodic LAU timer using a multiplier. In particular, the format is aControl Channel Descriptor information element identifier (IEI) insideRR System Information Type 3 message. 3GPP TS 44.018 V10.0.0 (2010),section 10.5.2.11 describes RR System Information Type 3 message.Section 10.5.2.11 of 3GPP TS 44.018 V10.0.0 (2010) specifies use ofoctet 4 to transmit the T3212 time-out value. Octet 5 can be added tocommunicate an extended T3212 timer or T3212_Multiplier. The extendedT3212 timer can be defined in a similar manner as that of T3312ext valueby using one or more octets.

FIG. 4 depicts an example manner that an MS can receive a periodic LAUtimer from a network. At 408, MS 404 can transmit a LOCATION AREA UPDATEREQUEST message to network 402. A suitable format of a LOCATION AREAUPDATE REQUEST is described for example in TS 24.008 section 9.2.15,although other formats can be used. Network 402 can include one or morecomputing devices that interact with MS 404 and HLR/HSS 406. Network 402can include an MSC, SGSN, or other device. MSC or SGSN can receive theLOCATION UPDATE REQUEST message. The SGSN is responsible for thedelivery of data packets from and to the mobile stations within itsgeographical service area. The SGSN can perform packet routing andtransfer, mobility management (attach/detach and location management),logical link management, and authentication and charging functions.

Home location register/home subscription server (HLR/HSS) 406 canperform security operations involving network 402 and MS 404. Securityoperations and insertion of subscriber data are authenticationoperations that make sure a device is permitted to use network and aredescribed generally in TS 24.008 as well as TS 23.060. In addition,HLR/HSS 406 can maintain subscription information concerning MS 404 aswell as other devices attached to network 402. In some embodiments,subscription information can include fields that store the periodic LAU,RAU, and TAU timer values for MS 404.

Network 402 determines whether MS 404 is a low mobility device or not.Network 402 can determine that MS 404 is a low mobility device bysubscription information in an HLR/HSS that indicates whether MS 404 isa low mobility device. Subscription information can be supplemented toindicate that MS 404 is a low mobility type device. In some cases, MS404 can inform network 402 that MS 404 is a low mobility using a fieldthat can be added to a LOCATION AREA UPDATE REQUEST or ATTACH REQUESTmessage specified in section 9.4.1 of TS 24.008, although other formatscan be used. The field can be one (1) bit. A network administrator canidentify subscription information as associated with a low mobilitydevice.

After performing security operations and updating subscriberinformation, at 410, network 402 transmits a LOCATION AREA UPDATE ACCEPTmessage to MS 404. The LOCATION AREA UPDATE ACCEPT message can bemodified to include a multiplier for a low mobility device. Section9.2.13 of TS 24.008 describes LOCATION AREA UPDATE ACCEPT messagecontent, although other formats can be used. In various embodiments,LOCATION AREA UPDATE ACCEPT message content is modified to include afield T3212_Multiplier, which stores a multiplier. FieldT3212_Multiplier can be 1 octet or 8 bits. However, the T3212_Multiplierfield can be other sizes. In various embodiments, each MS can receive adifferent multiplier value or the same multiplier value. In variousembodiments, the multiplier can increase linearly with increasing binaryvalues. In some cases, the multiplier can increase exponentially or in aquadratic manner.

For example, using a procedure of FIG. 2, MS 404 can use a periodic LAUtimer that is a product of the multiplier and a programmed timer value.

In some embodiments, periodic timer T3212 can be added to LOCATION AREAUPDATE ACCEPT message to transmit a new extended periodic LAU timer toan MS. An extended periodic LAU timer can be transmitted in 3 octets or24 bits. The extended periodic LAU timer can be defined in a similarmanner as that of T3312ext value.

FIG. 5 depicts a procedure for setting a timer for routing area updates.At 508, MS 504 issues a ROUTING AREA UPDATE REQUEST to network 502.Network 502 can include one or more SGSN that interact with MS 504 andHLR/HSS 506. A format of a ROUTING AREA UPDATE REQUEST is described insection 9.4.14 of TS 24.008 (2010), although other formats can be used.Security operations, subscriber data insertion, and/or determination ofwhether a device is low mobility can take place in a similar manner asdescribed with regard to FIG. 4. At 510, a ROUTING AREA UPDATE ACCEPTmessage is transmitted from network 502 to MS 504. ROUTING AREA UPDATEACCEPT message is described in section 9.4.15 of TS 24.008 (2010),although other formats can be used. An extended periodic RAU timer forRAU can be added to the ROUTING AREA UPDATE ACCEPT message as T3312extvalue. T3312ext value can be 3 octets or 24 bits. Other sizes of theextended periodic RAU timer can be used. Each timer can be sent fromHLR/HSS 506 to MS 504 through network 502. In some cases, SGSN ofnetwork 502 can decide the extended periodic RAU timer.

Accordingly, by transmitting an extended periodic RAU timer for routingarea updates, the time period between each periodic RAU can beincreased. Using the extended periodic RAU timer, the time period can beincreased beyond 31 decihours. By contrast, not using the extensiontimer makes the maximum time to be 31 decihours.

FIG. 6 depicts a procedure for setting a timer for tracking areaupdates. Network 602 can include one or more SGSN and/or MME thatinteract with MS 604 and HLR/HSS 606. At 608, MS 604 issues a TRACKINGAREA UPDATE REQUEST to network 602. A format of TRACKING AREA UPDATEREQUEST is described in TS 24.301 version 10.1.0 (2010), although otherformats can be used. Security operations, subscriber data insertion,and/or determination of whether a device is low mobility can take placein a similar manner as described with regard to FIG. 4. At 610, aTRACKING AREA UPDATE ACCEPT message is transmitted from network 602 toMS 604. A format of TRACKING AREA UPDATE ACCEPT is described in 3GPP TS24.301 (2010). An extended periodic TAU timer for TAU can be added tothe TRACKING AREA UPDATE ACCEPT message as T3412ext value, althoughother formats can be used to transmit T3412ext value. T3412ext value canbe 3 octets or 24 bits, although other values can be used. Each timercan be sent from HLR/HSS 606 to MS 604 through network 602. In somecases, MME of network 602 can decide the timer.

Accordingly, by transmitting an extended periodic TAU timer for trackingarea updates, the time period between each periodic TAU can beincreased. Using the extended periodic timer, the time period can beincreased beyond 31 decihours. By contrast, not using the extendedperiodic TAU timer makes the maximum time to be 31 decihours. Theextended periodic TAU timer can be defined in a similar manner as thatof T3312ext value.

An attach procedure can occur when powering-on an MS or when an MSenters a network. The MS registers with the network to receive servicesthat require registration. In an attach procedure, the MS transmits anattach request to the network and the network affirms the attach requestwith an attach accept message. Section 5.3.4 of 3GPP TS 24.301 version8.0.0 (2008) specifies that an attach accept message can include a timerT3412 that can be used to time periodic TAU update operations.Currently, however, under 3GPP TS 24.008 version 10.0.0 (2010), the GPRStimer can be at most 31 decihours. When many mobile stations use thenetwork for machine-to-machine communications, the network can becomeoverloaded with traffic. It may be desirable to increase the timebetween timed communications from mobile stations to the network.Various embodiments provide a manner to communicate extension timersusing attach accept messages. Extension timers can specify a longer timeperiod between communications to a network.

FIG. 7 depicts a procedure that can be used to transmit a timer forperiodic routing area updates in connection with an attach procedure. At708, to commence an attach procedure, MS 704 issues an attach request tonetwork 702. A format of an ATTACH REQUEST for UMTS/HSPA is describedfor example at section 9.4.1 of TS 24.008 (2010). An SGSN of network 702can receive the ATTACH REQUEST message.

Security operations, subscriber data insertion, and/or determination ofwhether a device is low mobility can take place in a similar manner asdescribed with regard to FIG. 4. At 710, an ATTACH ACCEPT message istransmitted from network 702 to MS 704. ATTACH ACCEPT message isdescribed at section 9.4.2 of TS 24.008 (2010). In various embodiments,the ATTACH ACCEPT message can be modified to include T3312ext value forperiodic RAU, although other formats can be used to transmit T3312ext.T3312ext value can be 3 octets or 24 bits.

At 712, MS 704 can transmit an ATTACH COMPLETE message to network 702 toindicate completion of attachment. For example, a format of an ATTACHCOMPLETE message is described in section 9.4.3 of TS 24.008 (2010).

The procedure of FIG. 7 can also be used to transmit a timer forperiodic TAU in connection with an attach procedure. At 708, to commencean attach procedure. MS 704 issues an ATTACH REQUEST message to network702. An ATTACH REQUEST message for LTE is described for example in TS24.301 (2010). An MME or SGSN in network 702 can receive the ATTACHREQUEST message. An MME can be a control-node for the LTEaccess-network. The MME can be responsible for idle mode UE (UserEquipment) tracking and paging procedure including retransmissions. TheMME can be involved in the bearer activation/deactivation process and isalso responsible for choosing the serving gateway S-GW/SGSN for a UE atthe initial attach and at time of intra-LTE handover involving CoreNetwork (CN) node relocation.

Security operations, subscriber data insertion, and/or determination ofwhether a device is low mobility can take place in a similar manner asdescribed with regard to FIG. 4. At 710, an ATTACH ACCEPT message istransmitted from network 702 to MS 704. ATTACH ACCEPT message isdescribed in TS 24.301 (2010). In various embodiments, the ATTACH ACCEPTmessage can be modified to include T3412ext value for periodic TAU,although other formats can be used to transmit T3412ext value. T3412extvalue can be 3 octets or 24 bits.

At 712, MS 704 can transmit an ATTACH COMPLETE message to network 702 toindicate completion of attachment. For example, a format of an ATTACHCOMPLETE message is described in TS 24.301 (2010).

For packet switched domain specific systems, periodic RAU or TAUfrequency can be controlled per device. In some cases, the maximum valuefor T3312 or T3412 can be 31 decihours. Given the large number of MTCdevices that may be deployed in future, this may still result in quite abit signaling overhead. Some embodiments attempt to increase a maximumtime of T3312/T3412 by changing units used for timer values. In someembodiments, binary coding can be added to indicate a GPRS timer valueis incremented in a multiple of 10 hours, 100 decihours, days, or otherdurations.

Timers T3312 and T3412 can be transmitted using a GPRS timer value. GPRSTimer can be specified in subclause 10.5.7.3 of TS 24.008. GPRS Timercan be transmitted in a type 3 information element that is 2 octets inlength. Octet 1 represents GPRS timer IE. In octet 2, bits 1 to 5represent the binary coded timer value and bits 6 to 8 define a unit ofthe timer value. In some embodiments, the timer value unit can beincreased beyond decihour to a 24 hour period. Accordingly, in someembodiments, the maximum timer value can be increased from 31 decihoursto 31 days. However, if the timer value unit is increased, then thetimer can be increased even more.

In some embodiments, bits 6 to 8 define the timer value unit for theGPRS timer as follows:

Bits 8 7 6 0 0 0 value is incremented in multiples of 2 seconds 0 0 1value is incremented in multiples of 1 minute 0 1 0 value is incrementedin multiples of decihours 0 1 1 value is incremented in multiples of 10hours 1 0 0 value is incremented in multiples of 24 hours 1 1 1 valueindicates that the timer is deactivated.For example, two timer increments can be added that are specified by 011and 100. Other increments of timers can be used. Another increment canbe added for value 110.

Of note, the Mobile Reachable timer of TS 24.008 (2010) can be derivedfrom location update timer T3212, routing area update timer T3312ext, ortracking update timer T3412ext. Corresponding to T33121T3412 in MS,networks also starts Mobile Reachable timer which by default is 4minutes greater than T3312/T3412.

FIG. 8 provides an example of a system in accordance with an embodiment.The system can be used in an MS, UE, MTC device, netbook, handheldcomputer, handheld phone, and so forth. Computer system 800 may includehost system 802 and display 822. Computer system 800 can be implementedin a handheld personal computer, mobile telephone, set top box, or anycomputing device. Any type of user interface is available such as akeypad, mouse, touch screen, and/or gesture or motion recognition. Hostsystem 802 may include chipset 805, processor 810, host memory 812,storage 814, graphics subsystem 815, and radio 820. Chipset 805 mayprovide intercommunication among processor 810, host memory 812, storage814, graphics subsystem 815, and radio 820. For example, chipset 805 mayinclude a storage adapter (not depicted) capable of providingintercommunication with storage 814.

Processor 810 may be implemented as Complex Instruction Set Computer(CISC) or Reduced Instruction Set Computer (RISC) processors, x86instruction set compatible processors, multi-core, or any othermicroprocessor or central processing unit. In various embodiments,processor 810 can be configured with instructions to perform techniquesdescribed herein.

Host memory 812 may be implemented as a volatile memory device such asbut not limited to a Random Access Memory (RAM), Dynamic Random AccessMemory (DRAM), or Static RAM (SRAM). Storage 814 may be implemented as anon-volatile storage device such as but not limited to a magnetic diskdrive, optical disk drive, tape drive, an internal storage device, anattached storage device, flash memory, battery backed-up SDRAM(synchronous DRAM), and/or a network accessible storage device.

Graphics subsystem 815 may perform processing of images such as still orvideo for display. An analog or digital interface may be used tocommunicatively couple graphics subsystem 815 and display 822. Forexample, the interface may be any of a High-Definition MultimediaInterface, DisplayPort, wireless HDMI, and/or wireless HD complianttechniques. Graphics subsystem 815 could be integrated into processor810 or chipset 805. Graphics subsystem 815 could be a stand-alone cardcommunicatively coupled to chipset 805.

Radio 820 may include one or more radios capable of transmitting andreceiving signals in accordance with applicable wireless standards suchas but not limited to any version of IEEE 802.11 and IEEE 802.16. Forexample, radio 820 may include at least a physical layer interface andmedia access controller. Radio 820 can include a baseband processor toperform techniques described herein.

Embodiments of the present invention may be implemented as any or acombination of: one or more microchips or integrated circuitsinterconnected using a motherboard, hardwired logic, software stored bya memory device and executed by a microprocessor, firmware, anapplication specific integrated circuit (ASIC), and/or a fieldprogrammable gate array (FPGA). The term “logic” may include, by way ofexample, software or hardware and/or combinations of software andhardware.

Embodiments of the present invention may be provided, for example, as acomputer program product which may include one or more machine-readablemedia having stored thereon machine-executable instructions that, whenexecuted by one or more machines such as a computer, network ofcomputers, or other electronic devices, may result in the one or moremachines carrying out operations in accordance with embodiments of thepresent invention. A machine-readable medium may include, but is notlimited to, floppy diskettes, optical disks, CD-ROMs (Compact Disc-ReadOnly Memories), and magneto-optical disks, ROMs (Read Only Memories),RAMs (Random Access Memories), EPROMs (Erasable Programmable Read OnlyMemories), EEPROMs (Electrically Erasable Programmable Read OnlyMemories), magnetic or optical cards, flash memory, or other type ofmedia/machine-readable medium suitable for storing machine-executableinstructions.

The drawings and the forgoing description gave examples of the presentinvention. Although depicted as a number of disparate functional items,those skilled in the art will appreciate that one or more of suchelements may well be combined into single functional elements.Alternatively, certain elements may be split into multiple functionalelements. Elements from one embodiment may be added to anotherembodiment. For example, orders of processes described herein may bechanged and are not limited to the manner described herein. Moreover,the actions of any flow diagram need not be implemented in the ordershown; nor do all of the acts necessarily need to be performed. Also,those acts that are not dependent on other acts may be performed inparallel with the other acts. The scope of the present invention,however, is by no means limited by these specific examples. Numerousvariations, whether explicitly given in the specification or not, suchas differences in structure, dimension, and use of material, arepossible. The scope of the invention is at least as broad as given bythe following claims.

1-22. (canceled)
 23. An apparatus comprising: logic to transmit arequest message to a network, the request message comprising one of atracking area update request message, a location updating requestmessage, and a routing area update request message; logic to receive anaccept message, the accept message including an extended timer value andthe accept message comprising one of a tracking area update acceptmessage, a location updating accept message, and a routing area updateaccept message; logic to perform a tracking area update procedure timedin accordance with the extended timer value in response to receipt of atracking area update accept message; logic to perform a locationupdating procedure timed in accordance with the extended timer value inresponse to receipt of a location updating accept message; and logic toperform a routing area updating procedure timed in accordance with theextended timer value in response to receipt of a routing area updateaccept message.
 24. The apparatus of claim 23, wherein the extensiontimer comprises one of a T3212ext value for a location area updateprocedure, a T3312ext value for a routing area update procedure, and aT3412ext value for a tracking area update procedure.
 25. The apparatusof claim 23, wherein the tracking area update accept message comprises aTRACKING AREA UPDATE ACCEPT message described in 3GPP TS 24.301 (2010);the location updating accept message comprises a LOCATION AREA UPDATEACCEPT message described in TS 24.008 (2010); and the routing areaupdate accept message comprises a ROUTING AREA UPDATE ACCEPT messagedescribed in TS 24.008 (2010).
 26. A computer-readable medium comprisinginstructions stored thereon, which when executed by a computer, causethe computer to: request transmission of an attach request message to anetwork; recognize receipt of an attach accept message, the attachaccept message including an extended timer value; request performance ofa tracking area update procedure in accordance with timing indicated bythe extended timer value in response to the extended timer value beingassociated with a tracking area update procedure; and requestperformance of a routing area update procedure in accordance with timingindicated by the extended timer value in response to the extended timervalue being associated with a routing area update procedure.
 27. Themedium of claim 26, wherein the attach accept message comprises anATTACH ACCEPT message described in TS 24.008 (2010).
 28. The medium ofclaim 26, wherein the extension timer comprises one of a T3412ext valuefor a tracking area update procedure and a T3312ext value for a routingarea update procedure.
 29. A computer-readable medium comprisinginstructions stored thereon, which when executed by a computer, causethe computer to: request transmission of a request message to a network,the request message comprising one of a tracking area update requestmessage, a location updating request message, and a routing area updaterequest message; recognize receipt of an accept message, the acceptmessage including an extended timer value and the accept messagecomprising one of a tracking area update accept message, a locationupdating accept message, and a routing area update accept message;request performance of a tracking area update procedure timed inaccordance with the extended timer value in response to receipt of atracking area update accept message; request performance of a locationupdating procedure timed in accordance with the extended timer value inresponse to receipt of a location updating accept message; and requestperformance of a routing area updating procedure timed in accordancewith the extended timer value in response to receipt of a routing areaupdate accept message.
 30. The computer-readable medium of claim 29,wherein the extension timer value comprises one of a T3412ext value fora tracking area update, a T3212ext value for a location area update, anda T3312ext value for a routing area update.
 31. The computer-readablemedium of claim 29, wherein the tracking area update accept messagecomprises a TRACKING AREA UPDATE ACCEPT message described in 3GPP TS24.301 (2010); the location updating accept message comprises a LOCATIONAREA UPDATE ACCEPT message described in TS 24.008 (2010); and therouting area update accept message comprises a ROUTING AREA UPDATEACCEPT message described in TS 24.008 (2010).
 32. An apparatuscomprising: logic to transmit a request message to a network, therequest message comprising one of a tracking area update requestmessage, a location updating request message, and a routing area updaterequest message; logic to receive an accept message, the accept messageincluding an extended timer value and the accept message comprising oneof a tracking area update accept message, a location updating acceptmessage, and a routing area update accept message; logic to perform atracking area update procedure timed in accordance with the extendedtimer value in response to receipt of a tracking area update acceptmessage; logic to perform a location updating procedure timed inaccordance with the extended timer value in response to receipt of alocation updating accept message; and logic to perform a routing areaupdating procedure timed in accordance with the extended timer value inresponse to receipt of a routing area update accept message.
 33. Theapparatus of claim 32, wherein the extension timer value comprises oneof a T3412ext value for a tracking area update, a T3212ext value for alocation area update, and a T3312ext value for a routing area update.34. The apparatus of claim 32, wherein the tracking area update acceptmessage comprises a TRACKING AREA UPDATE ACCEPT message described in3GPP TS 24.301 (2010); the location updating accept message comprises aLOCATION AREA UPDATE ACCEPT message described in TS 24.008 (2010); andthe routing area update accept message comprises a ROUTING AREA UPDATEACCEPT message described in TS 24.008 (2010).
 35. A system comprising:at least one antenna; a radio communicatively coupled to the at leastone antenna; and a processor configured to: request transmission of anattach request message to a network; recognize receipt of an attachaccept message, the attach accept message including an extended timervalue; request performance of a tracking area update procedure inaccordance with timing indicated by the extended timer value in responseto the extended timer value being associated with a tracking area updateprocedure; and request performance of a routing area update procedure inaccordance with timing indicated by the extended timer value in responseto the extended timer value being associated with a routing area updateprocedure.
 36. The system of claim 35, wherein the attach accept messagecomprises an ATTACH ACCEPT message described in TS 24.008 (2010). 37.The system of claim 35, wherein the extension timer comprises one of aT3412ext value for a tracking area update and a T3312ext value for arouting area update.
 38. The system of claim 35, further comprising oneor more of: a touch screen interface, gesture recognition, and motionrecognition devices.
 39. A system comprising: at least one antenna; aradio communicatively coupled to the at least one antenna; and aprocessor configured to: request transmission of a request message to anetwork, the request message comprising one of a tracking area updaterequest message, a location updating request message, and a routing areaupdate request message; recognize receipt of an accept message, theaccept message including an extended timer value and the accept messagecomprising one of a tracking area update accept message, a locationupdating accept message, and a routing area update accept message;request performance of a tracking area update procedure timed inaccordance with the extended timer value in response to receipt of atracking area update accept message; request performance of a locationupdating procedure timed in accordance with the extended timer value inresponse to receipt of a location updating accept message; and requestperformance of a routing area updating procedure timed in accordancewith the extended timer value in response to receipt of a routing areaupdate accept message.
 40. The system of claim 39, wherein the extensiontimer value comprises one of a T3412ext value for a tracking areaupdate, a T3212ext value for a location area update, and a T3312extvalue for a routing area update.
 41. The system of claim 39, wherein thetracking area update accept message comprises a TRACKING AREA UPDATEACCEPT message described in 3GPP TS 24.301 (2010); the location updatingaccept message comprises a LOCATION AREA UPDATE ACCEPT message describedin TS 24.008 (2010); the routing area update accept message comprises aROUTING AREA UPDATE ACCEPT message described in TS 24.008 (2010). 42.The system of claim 39, further comprising one or more of: a touchscreen interface, gesture recognition, and motion recognition devices.